Taiwan Yiyun Space Cloud Server Console Usage Instructions And Frequently Asked Questions Graphic And Text Answers

2026-05-19 13:21:28
Current Location： Blog > Taiwan Server

1.

first login and console overview

1) login method: use the yiyun space account to enter the console. account password and two-step verification code (2fa) are supported.
2) dashboard information: displays the number of instances, bandwidth usage, traffic statistics, alarms and unfinished tasks.
3) resource quota: check the remaining quota of cpu cores, memory, disks and public ip on the right side of the dashboard.
4) quick operation: there are power on/shutdown/restart/snapshot/reinstall system buttons on the right side of the instance. click to take effect.
5) suggested verification: when logging in for the first time, check that the time zone of the console is taipei time, and confirm that the email address + mobile phone number are bound.

2.

example of creating and configuring a cloud host (vps)

1) creation steps: select taiwan node → select image (ubuntu 22.04/centos 7) → specifications → network bandwidth → create.
2) sample configuration: 4 vcpu / 8 gb ram / 80 gb nvme / 100 mbps bandwidth, suitable for small and medium-sized e-commerce or wordpress sites.
3) startup time: the average deployment time is 60–120 seconds. the console displays the instance ip and login credentials.
4) network performance: the average delay to taipei nodes is 5–20 ms, and the peak public network bandwidth test can reach 95 mbps.
5) cost estimate: the monthly billing example is nt$1,200/month (example only, the actual price will be determined by the platform).

3.

disks, snapshots and backup strategies

1) disk type: it is recommended to use nvme ssd to increase iops. ordinary ssd is suitable for low-cost backup disks.
2) snapshot frequency: it is recommended to take automatic daily snapshots for key businesses and save them on a 7-day rolling basis; the database uses hourly incremental backups.
3) recovery drill: perform recovery from snapshot drills at least once a quarter to ensure data consistency and application availability.
4) example data: a customer's production database (mysql) is 10 gb. hourly incremental backup is used. the daily increment is about 200 mb. the total bandwidth impact is about 1.6 gb per day.
5) cost consideration: snapshot storage is billed by gb. 80 gb snapshots retained for 7 days account for approximately 560 gb of storage space.

4.

domain name resolution and cdn acceleration configuration guide

1) domain name resolution: bind the domain name in the console and add an a record pointing to the public ip of the instance. it is recommended that the ttl be set to 300 seconds.
2) cdn access: enable cdn in yiyun space, and configure the origin site as the public ip address of the cloud host or the load balancer address.
3) caching rules: the cache time of static resources (.css/.js/.jpg/.png) can be set to 7 days, and dynamic pages use the back-to-origin strategy.
4) a real case: when the traffic of a certain media site surged, the static hit rate increased to 92% after turning on cdn, and the origin site bandwidth was reduced by 70%.
5) https certificate: cdn can host ssl certificates and supports let's encrypt automatic renewal, reducing the burden of origin site certificate management.

5.

ddos defense and security reinforcement practices

1) protection level: it is recommended to use edge ddos cleaning combined with instance-level firewalls. edge mitigation can withstand dozens of gbps attacks.
2) trigger threshold: set an abnormal traffic alarm to trigger manual intervention when the inflow traffic exceeds 200 mbps within 2 minutes.
3) protection strategy: set rate limits and black and white lists for tcp syn, udp flooding, and http request storms respectively.
4) example case: an e-commerce company encountered a syn flood attack during a holiday promotion. after cleaning was enabled, the peak attack dropped from 5 gbps to below normal traffic, and the order system was not interrupted.
5) daily operation and maintenance: enable automatic system updates, change ssh ports, prohibit root direct login, use key login and configure fail2ban.

6.

frequently asked questions and step-by-step troubleshooting process

1) unable to log in to ssh: check whether the security group rules open port 22, whether the instance is started, and whether the keys match.
2) slow page loading: check the cpu/memory/disk io, slow database query, and whether the static resources are not connected to the cdn, causing the static resources to return to the source.
3) domain name resolution does not take effect: confirm that the a record of the domain name points to the correct ip and check the ttl and local dns cache.
4) high traffic leads to soaring costs: check the traffic billing details, consider accessing cdn, speed limiting policy or using annual and monthly subscription bandwidth.
5) step-by-step troubleshooting example: when the request delay of a certain site is high, use top, iostat, iftop and curl -i to check the bottleneck, and expand or optimize based on the results.

7.

performance monitoring and expansion suggestions

1) monitoring indicators: focus on cpu usage, remaining memory, disk iops, network throughput and response time.
2) automatic expansion: for stateless applications, load balancing + automatic scaling groups can be used, and cpu 80% is set as the trigger threshold.
3) database expansion: master-slave replication or read-write separation can transfer read traffic to the slave database to reduce the pressure on the master database.
4) configuration example: under high concurrency conditions, the web layer is expanded from one 4vcpu/8gb to three units with the same specifications. after load balancing and offloading, the response time drops by about 60%.
5) cost-performance balance: evaluate vertical expansion (upgrading instance specifications) or horizontal expansion (increasing the number of instances) based on qps and target rps.

attached table: common instance specifications and reference performance

specification vcpu memory disk bandwidth
entry type 2 4gb 40gb ssd 50mbps
standard type 4 8gb 80gb nvme 100mbps
high efficiency 8 16 gb 160gb nvme 200mbps
taiwan server
Tags：taiwan cloud server art cloud space vps console teaching host management cdn ddos defense domain name resolution server configuration More»
Latest articles
Expansion Plan: Overview Of Vietnam Cloud Host Vps Rental Elastic Scaling And Load Balancing Implementation Methods
Taiwan Yiyun Space Cloud Server Console Usage Instructions And Frequently Asked Questions Graphic And Text Answers
Choose An American Host Cn2 With Appropriate Bandwidth And Protection Level. Solution Recommendations And Case Sharing
Malaysian Server Name Directory, Enterprise-level Cluster Naming Instances And Directory Management Methods
How To Identify Reliable Korean Vps Purchasing Services To Avoid Subsequent Operation And Maintenance Risks
Taxation And Contract Risk Assessment: Can Singapore Servers Be Transferred? Practical Guide
Softbank And Soft Layer Comparison Soft Layer Japan Cn2’s Advantages In Enterprise-level Deployments
From Novice To Expert, Common Misunderstandings And Correction Methods In Selecting Pubg Vietnam Server
Taiwan Cloud Server Recommended Physical Machine Performance Optimization And Model Selection Guide
Comprehensive Consideration Of Performance Flexibility And Regional Acceleration: Key Points For Selecting Cloud Hosts For Taiwan Station Clusters
Popular tags
Taiwan Cloud Server Qps Website Security Website Performance Station Group Server Node Setup List Of Costs For Taiwan-based Original Ips Chunghwa Telecom Connection Problem Cost Comparison Concurrent Access To Multiple Stores Matching Teammates Promotions Review Station Cluster Operation And Maintenance Cross-border Seo Optimization Website Setup Console Teaching Data Synchronization Gslb Advertising Original Ecology Vps Skills Dynamic Ip Taiwan Native IP Market Network Infrastructure Competitiveness Service Recommendation
Related Articles